Systems and methods for detecting anomalous behaviors based on temporal profile

ABSTRACT

The present disclosure is directed to a method of detecting anomalous behaviors based on a temporal profile. The method can include collecting, by a control system comprising a processor and memory, a set of network data communicated by a plurality of network nodes over a network during a time duration. The method can include identifying, by the control system, one or more seasonalities from the set of network data. The method can include generating, by the control system, a temporal profile based on the one or more identified seasonalities. The method can include detecting, by the control system and based on the temporal profile, an anomalous behavior performed by one of the plurality of network nodes. The method can include identifying, by the control system and based on the temporal profile, a root cause for the anomalous behavior.

BACKGROUND

The present invention relates generally to the field of computersecurity. In general, a computing device may have one or morevulnerabilities that can be leveraged by malicious code to compromisethe computing device. Malicious code may also be introduced onto acomputing device by deceiving a user. Malicious code running on acompromised machine may install additional malware components. Computersecurity is improved through the detection of malicious software(“malware”) that either uses malicious code to exploit vulnerabilities(or deceive users) and repurpose infected computers or performsmalicious actions once installed on a compromised host. Once malware isdetected and the exploits are understood, security systems may bedesigned to recognize and block the malware and the vulnerabilities maybe patched.

BRIEF SUMMARY

In one aspect, the present disclosure is directed to a method fordetecting anomalous behaviors based on a temporal profile. The methodcan include collecting, by a control system comprising a processor andmemory, a set of network data communicated by a plurality of networknodes over a network during a time duration. The method can includeidentifying, by the control system, one or more seasonalities from theset of network data. The method can include generating, by the controlsystem, a temporal profile based on the one or more identifiedseasonalities. The method can include detecting, by the control systemand based on the temporal profile, an anomalous behavior performed byone of the plurality of network nodes. The method can includeidentifying, by the control system and based on the temporal profile, aroot cause for the anomalous behavior.

In some embodiments, the method can further include switching, by thecontrol system, from a data collection mode to an anomaly detection modein response to the generation of the temporal profile.

In some embodiments, the set of network data includes at least one of: aplurality of raw data packets over the network, respective source IPaddresses of the plurality of raw data packets, respective destinationIP addresses of the plurality of raw data packets, respective source TCPports of the plurality of raw data packets, respective destination TCPports of the plurality of raw data packets, respective source UDP portsof the plurality of raw data packets, respective destination UDP portsof the plurality of raw data packets, and respective data sizes of theplurality of raw data packets.

In some embodiments, the method can further include segmenting, by thecontrol system, the time duration into a plurality of monitoring timeperiods. The method can further include grouping, by the control systembased on a plurality of timestamps of the set of network data, the setof network data into respective subsets of the plurality of monitoringtime periods. The method can further include determining, by the controlsystem, the one or more seasonalities based on an occurrence rateassociated with each of the subset of the monitoring time periods.

In some embodiments, the method can further include determining, by thecontrol system, a network flow associated with the anomalous behaviorusing highest magnitude interaction analysis. In some embodiments, themethod can further include identifying, by the control system, thenetwork nodes associated with the network flow.

In some embodiments, the method can further include collecting, by thecontrol system, a second set of network data communicated by theplurality of network nodes over the network during a second timeduration. In some embodiments, the method can further includeidentifying, by the control system, one or more detection modeseasonalities from the second set of network data. In some embodiments,the method can further include comparing, by the control system, thedetection mode seasonalities with the temporal profile to calculate aconfidence margin. In some embodiments, the method can further includedetecting, by the control system, an anomalous behavior based on thecalculated confidence margin exceeding a predetermined threshold.

In some embodiments, the method can further include identifying, by thecontrol system, from the set of network data, a network communicationbetween two network nodes, wherein at least one of the network nodes ison a list of known malicious network nodes. In some embodiments, themethod can further include identifying, by the control system, one ormore malicious seasonalities of the identified network communication. Insome embodiments, the method can further include generating, by thecontrol system, a malicious temporal profile based on the one or moreidentified malicious seasonalities. In some embodiments, the method canfurther include comparing, by the control system, the one or moreseasonalities to the malicious temporal profile to determine a maliciousnetwork communication with an unknown network node. In some embodiments,the method can further include adding, by the control system, theunknown network node to the list of known malicious network nodes.

In some embodiments, the method can further include identifying, by thecontrol system, from the set of network data, a network communicationbetween two network nodes, wherein at least one of the network nodes ison a list of known trusted network nodes. In some embodiments, themethod can further include identifying, by the control system, one ormore trusted seasonalities of the identified network communication. Insome embodiments, the method can further include generating, by thecontrol system, a trusted temporal profile based on the one or moreidentified trusted seasonalities. In some embodiments, the method canfurther include comparing, by the control system, the one or moreseasonalities to the trusted temporal profile to determine a trustednetwork communication with an unknown network node. In some embodiments,the method can further include adding, by the control system, theunknown network node to the list of known trusted network nodes.

In another aspect, the present disclosure is directed to a computingdevice configured to detect anomalous behaviors based on a temporalprofile. The computing device includes a memory, and one or moreprocessors operatively coupled to the memory. The one or more processorsare configured to collect a set of network data communicated by aplurality of network nodes over a network during a time duration. Theone or more processors are configured to identify one or moreseasonalities from the set of network data. The one or more processorsare configured to generate a temporal profile based on the one or moreidentified seasonalities. The one or more processors are configured todetect, based on the temporal profile, an anomalous behavior performedby one of the plurality of network nodes. The one or more processors areconfigured to identify, based on the temporal profile, a root cause forthe anomalous behavior.

In some embodiments, the one or more processors are further configuredto switch from a data collection mode to an anomaly detection mode inresponse to the generation of the temporal profile.

In some embodiments, the set of network data includes at least one of: aplurality of raw data packets over the network, respective source IPaddresses of the plurality of raw data packets, respective destinationIP addresses of the plurality of raw data packets, respective source TCPports of the plurality of raw data packets, respective destination TCPports of the plurality of raw data packets, respective source UDP portsof the plurality of raw data packets, respective destination UDP portsof the plurality of raw data packets, and respective data sizes of theplurality of raw data packets.

In some embodiments, the one or more processors are further configuredto segment the time duration into a plurality of monitoring timeperiods. The one or more processors are further configured to group,based on a plurality of timestamps of the set of network data, the setof network data into respective subsets of the plurality of monitoringtime periods. The one or more processors are further configured todetermine the one or more seasonalities based on an occurrence rateassociated with each of the subset of the monitoring time periods.

In some embodiments, the one or more processors are further configuredto determine a network flow associated with the anomalous behavior usinghighest magnitude interaction analysis. In some embodiments, the one ormore processors are further configured to identify the network nodesassociated with the network flow.

In some embodiments, the one or more processors are further configuredto collect a second set of network data communicated by the plurality ofnetwork nodes over the network during a second time duration. In someembodiments, the one or more processors are further configured toidentify one or more detection mode seasonalities from the second set ofnetwork data. In some embodiments, the one or more processors arefurther configured to compare the detection mode seasonalities with thetemporal profile to calculate a confidence margin. In some embodiments,the one or more processors are further configured to detect an anomalousbehavior based on the calculated confidence margin exceeding apredetermined threshold.

In some embodiments, the one or more processors are further configuredto identify, from the set of network data, a network communicationbetween two network nodes, wherein at least one of the network nodes ison a list of known malicious network nodes. In some embodiments, the oneor more processors are further configured to identify one or moremalicious seasonalities of the identified network communication. In someembodiments, the one or more processors are further configured togenerate a malicious temporal profile based on the one or moreidentified malicious seasonalities. In some embodiments, the one or moreprocessors are further configured to compare the one or moreseasonalities to the malicious temporal profile to determine a maliciousnetwork communication with an unknown network node. In some embodiments,the one or more processors are further configured to add the unknownnetwork node to the list of known malicious network nodes.

In some embodiments, the one or more processors are further configuredto identify, from the set of network data, a network communicationbetween two network nodes, wherein at least one of the network nodes ison a list of known trusted network nodes. In some embodiments, the oneor more processors are further configured to identify one or moretrusted seasonalities of the identified network communication. In someembodiments, the one or more processors are further configured togenerate a trusted temporal profile based on the one or more identifiedtrusted seasonalities. In some embodiments, the one or more processorsare further configured to compare the one or more seasonalities to thetrusted temporal profile to determine a trusted network communicationwith an unknown network node. In some embodiments, the one or moreprocessors are further configured to add the unknown network node to thelist of known trusted network nodes.

In yet another aspect, the present disclosure is directed to anon-transitory computer readable medium storing program instructions.The program instructions cause one or more processors to collect a setof network data communicated by a plurality of network nodes over anetwork during a time duration. The program instructions cause the oneor more processors to identify one or more seasonalities from the set ofnetwork data. The program instructions cause the one or more processorsto generate a temporal profile based on the one or more identifiedseasonalities. The program instructions cause the one or more processorsto detect, based on the temporal profile, an anomalous behaviorperformed by one of the plurality of network nodes. The programinstructions cause the one or more processors to identify, based on thetemporal profile, a root cause for the anomalous behavior.

In some embodiments, the program instructions cause the one or moreprocessors to collect a second set of network data communicated by theplurality of network nodes over the network during a second timeduration. In some embodiments, the program instructions cause the one ormore processors to identify one or more detection mode seasonalitiesfrom the second set of network data. In some embodiments, the programinstructions cause the one or more processors to compare the detectionmode seasonalities with the temporal profile to calculate a confidencemargin. In some embodiments, the program instructions cause the one ormore processors to detect an anomalous behavior based on the calculatedconfidence margin exceeding a predetermined threshold.

In some embodiments, the program instructions cause the one or moreprocessors to identify, from the set of network data, a networkcommunication between two network nodes, wherein at least one of thenetwork nodes is on a list of known malicious network nodes. In someembodiments, the program instructions cause the one or more processorsto identify one or more malicious seasonalities of the identifiednetwork communication. In some embodiments, the program instructionscause the one or more processors to generate a malicious temporalprofile based on the one or more identified malicious seasonalities. Insome embodiments, the program instructions cause the one or moreprocessors to compare the one or more seasonalities to the malicioustemporal profile to determine a malicious network communication with anunknown network node. In some embodiments, the program instructionscause the one or more processors to add the unknown network node to thelist of known malicious network nodes.

In some embodiments, the program instructions cause the one or moreprocessors to identify, from the set of network data, a networkcommunication between two network nodes, wherein at least one of thenetwork nodes is on a list of known trusted network nodes. In someembodiments, the program instructions cause the one or more processorsto identify one or more trusted seasonalities of the identified networkcommunication. In some embodiments, the program instructions cause theone or more processors to generate a trusted temporal profile based onthe one or more identified trusted seasonalities. In some embodiments,the program instructions cause the one or more processors to compare theone or more seasonalities to the trusted temporal profile to determine atrusted network communication with an unknown network node. In someembodiments, the program instructions cause the one or more processorsto add the unknown network node to the list of known trusted networknodes.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other aspects and features of the present embodiments willbecome apparent to those ordinarily skilled in the art upon review ofthe following description of specific embodiments in conjunction withthe accompanying figures, wherein:

FIG. 1 is a block diagram illustrating one embodiment of computingsystems in a network environment, according to an exemplary embodiment.

FIG. 2 is a block diagram illustrating one embodiment of a generalarchitecture of a computing device useful in connection with the systemsand methods described herein, according to an exemplary embodiment.

FIG. 3 is a diagrammatic view of one embodiment of a traffic model,according to an exemplary embodiment.

FIG. 4 is a flow diagram of a method for detecting anomalous behaviorsbased on a temporal profile, according to an exemplary embodiment.

DETAILED DESCRIPTION

Following below are more detailed descriptions of various conceptsrelated to, and embodiments of, methods, apparatuses, and systemsintroduced above. The various concepts introduced above and discussed ingreater detail below may be implemented in any of numerous ways, as theconcepts described are not limited to any particular manner ofembodiment. Examples of specific embodiments and applications areprovided primarily for illustrative purposes.

In general, a computing device connected to a data network may have oneor more vulnerabilities that can be leveraged to compromise thecomputing device. Vulnerabilities include unintentional program flaws,such as a buffer with inadequate overrun prevention, and intentionalholes, such as an undisclosed programmatic backdoor. Malicious code can,and has been, developed to exercise these various vulnerabilities toyield the execution of code under the control of an attacker. Maliciouscode implemented to target a particular vulnerability is sometimesreferred to as an exploit. For example, malicious code may access anapparently benign interface and cause a buffer overflow resulting in theplacement of unauthorized code in the execution stack where it may berun with elevated privileges. Such an attack could execute an exploitcausing the buffer overflow and enabling an unauthorized party to obtainadministrative control over the computing device. Commonly, the exploitcode downloads additional components of the malware, and modifies theoperating system to become persistent. The computing device, nowcompromised, may be used for further attacks on other computing devicesin the network or put to other malicious purposes, such as thecollection and exfiltration of sensitive data.

Some compromised machines are configured to communicate with a remoteendpoint, e.g., a command and control (“C&C”) system. For example, acompromised machine may check in with a C&C host to receive instructionsfor how the compromised machine should be used (e.g., to sendunsolicited e-mails, i.e., “spam,” or to participate in a distributeddenial-of-service attack, i.e., “D-DOS”). A compromised machine issometimes referred to as a “Bot” or a “Zombie” machine. A network ofthese machines is often referred to as a “botnet.”

Malicious code may be embodied in malicious software (“malware”). Asused herein, malware includes, but is not limited to, computer viruses,worms, Trojans, rootkits, and spyware. Malware may generally include anysoftware that circumvents user or administrative controls. Maliciouscode may be created by an individual for a particular use. Exploits maybe created to leverage a particular vulnerability, and then adopted forvarious uses, e.g., in scripts or network attacks. Generally, becausenew forms of malicious behavior are designed and implemented on aregular basis, it is desirable to recognize previously unknown maliciouscode.

In some instances, malware may be designed to avoid detection. Forexample, malware may be designed to load into memory before malwaredetection software starts during a boot-up phase. Malware may bedesigned to integrate into an operating system present on an infectedmachine. Malware may bury network communication in apparently benignnetwork communication. Malware may connect to legitimate networkendpoints to obscure connections to control servers or other targets. Insome instances, malware behaves in an apparently benign manner until atrigger event, e.g., a set day, arrives. In some instances, malware isreactive to environmental conditions. For example, malware may bedesigned to behave in an apparently benign manner in the presence ofmalware detection software.

Suspicious computer code may be identified as malware by observinginteractions between the suspicious computer code and remote networkendpoints. Suspicious computer code may generate or receive data packetsvia a data network. For example, if a data packet has a source ordestination endpoint matching a known command and control (“C&C”)server, then the code may be malicious. Likewise, if content of a datapacket is consistent with traffic models (“signatures”) for the trafficproduced by known malicious code, then the code may be malicious. Awatch-list of known or suspected malicious servers (e.g., C&C servers)is maintained and a catalog of traffic models is maintained. When a setof communicated data packets is classified as malicious using thewatch-list, the catalog is updated with a model of the data packets.When a set of communicated data packets is classified as malicious usingthe catalog of traffic models, the watch-list is updated with one ormore endpoints data from the data packets.

Using the signatures to identify malicious network activities mayprovide precise detection. However, the signatures are generally builtupon traffic models that have been created and lack temporalcharacteristics. Moreover, the malicious network activities can evolveor vary over time at a rapid pace. Thus, relying solely on suchsignatures may negatively affect the capability to quickly andeffectively identify the malicious network activities. The presentdisclosure provides various embodiments of systems and methods to solvesuch a technical problem.

The disclosed system can generate a temporal profile based on one ormore seasonalities of network data shared by a number of network nodes.For example, the disclosed system can collect a set of raw network datathat a number of network nodes used to communicate with each otherduring a time duration. In response to collecting the raw network data,the system can identify one or more behaviors and associate the one ormore behaviors with respective seasonalities (e.g., day vs. night, workhours vs. breaks, work days vs. weekends). A temporal profile can begenerated based on such associations between the behaviors and theseasonalities. The system can communicate, interface, or otherwiseintegrate with a threat communication system to define, categorize, orotherwise identify characteristics of the behaviors in the temporalprofile. For example, some behaviors may be identified as communicatingwith an unrecognized endpoint during midnights; some behaviors may beidentified as communicating with a suspicious endpoint every Monday; andsome behaviors may be identified as communicating with a maliciousendpoint (a C&C node) every week. Using the temporal profile, the systemcan determine that some of the behaviors may be anomalous based on thecharacteristics of the behaviors (e.g., a destination, a source, asignature, etc.) and respective seasonalities. Further, rather thansimply identifying an anomalous behavior, the system can pinpoint,determine, or otherwise identify a root cause for the anomalous behaviorusing the temporal profile. As such, the system cannot only reduce thelikelihood of false alarms but also shorten the time for the anomalous(or deemed as malicious) behaviors to be addressed.

FIG. 1 is a block diagram illustrating one embodiment of computingsystems in a network environment 100. The network environment 100 caninclude a plurality of network nodes 102, 104, and 106 communicatingwith each other and/or one or more remote endpoints 150 via a datanetwork 110. The network environment 100 can include or otherwiseinterface with a threat detection system 120 and a control system 130.The threat detection system 120 and the control system 130 can observe,monitor, and otherwise mange the communications of the network nodes102-106. In some embodiments, the threat detection system 120 can store,maintain, or otherwise manage a watch-list of suspect endpoints and acatalog of traffic models characterizing malicious network activities;and the control system 130 can generate a temporal profile based onbehaviors and respective seasonalities identified from network data overthe network 110 (e.g., raw network data that the network nodes 102-106communicate with each other and the endpoints 150). Although the threatdetection system 120 and the control system 130 are each represented asseparate from each of the network nodes 102-106, the threat detectionsystem 120 and the control system 130 can be integrated within each ofthe network nodes 102-106 itself while remaining within the scope of thepresent disclosure.

Each of the network nodes 102-106 may be any kind of computing device,including but not limited to, a laptop, desktop, tablet, electronic pad,personal digital assistant, smart phone, video game device, television,server, kiosk, or portable computer. In other embodiments, each of thenetwork nodes 102-106 may be a virtual machine. Each of the networknodes 102-106 may be single-core, multi-core, or a cluster. Each of thenetwork nodes 102-106 may operate under the control of an operatingsystem, such as any of the operating systems from Apple, Inc. (e.g., OSX or iOS), from Microsoft, Inc. (e.g., Windows NT, MSCS, Windows XP,Windows Server 2008, Windows Server Failover Clustering, Windows 7, orWindows 8), from Google Inc. (e.g., Chrome OS or Android), or Bell Lab'sUNIX and its derivatives (e.g., BSD, FreeBSD, NetBSD, Linux, Solaris,AIX, or HP/UX). Generally, each of the network nodes 102-106 may be anycomputing system susceptible to infection by malware, that is, anycomputing system. In some embodiments, each of the network nodes 102-106is a computing device 200, as illustrated in FIG. 2 and described below.

Each of the network nodes 102-106 may communicate with each other and/orone or more remote endpoints 150 via the data network 110. The network110 can be a local-area network (LAN), such as a company intranet, ametropolitan area network (MAN), or a wide area network (WAN), such asthe Internet and the World Wide Web. The network 110 may be any typeand/or form of network and may include any of a point-to-point network,a broadcast network, a wide area network, a local area network, atelecommunications network, a data communication network, a computernetwork, an asynchronous transfer mode (ATM) network, a synchronousoptical network (SONET), a wireless network, an optical fiber network,and a wired network. In some embodiments, there can be multiple networks110 between participants, for example a smart phone typicallycommunicates with Internet servers via a wireless network connected to aprivate corporate network connected to the Internet. The network 110 maybe public, private, or a combination of public and private networks. Thetopology of the network 110 may be a bus, star, ring, or any othernetwork topology capable of the operations described herein.

The remote endpoints 150 may be network addressable endpoints. Forexample, a remote endpoint 150 may be a data server, a web site host, adomain name system (DNS) server, a router, or a personal computingdevice. A remote endpoint 150 may be represented by a network address,e.g., domain name or an IP address. An Internet Protocol (“IP”) addressmay be an IPv4 address, an IPv6 address, or an address using any othernetwork addressing scheme. In some embodiments, a remote endpoint 150 isan un-resolvable network address, that is, it may be an address that isnot associated with a network device. Network communication to anun-resolvable address will fail until a network device adopts theaddress. For example, malware may attempt to communicate with a domainname that is not in use.

In some embodiments, the threat detection system 120 may be a distinctcomputing system monitoring the communications between the network nodes102-106 and the remote endpoints 150. For example, the network nodes102-106 and the threat detection system 120 may communicate with thenetwork 110 via a shared router or switch. The threat detection system120 may sniff packets on a local network, e.g., a network within a localcomputing environment that includes at least the network nodes 102-106and the threat detection system 120. In some embodiments, the networknodes 102-106 may each be a virtual machine and the threat detectionsystem 120 may be part of the virtual machine monitor (“VMM”).

The threat detection system 120 may maintain a watch-list of suspectendpoints and a catalog of traffic models characterizing maliciousnetwork activity. Generally, a watch-list of suspect endpoints is a setof addresses corresponding to one or more of the remote endpoints 150that are suspected of engaging in malicious network activity. Forexample, an address for a remote endpoint that is identified as a C&Cserver may be added to a watch-list (sometimes referred to as a “blacklist”). Network communication routed to or from an endpoint on awatch-list may be blocked to prevent operation of malware, such as abotnet. Generally, a traffic model characterizing malicious networkactivity may be any information set used to recognize network traffic.An example model for recognizing messages between a specific malwareloader, a Pushdo loader, and its associated C&C server, shall bediscussed with respect to FIG. 3. Generally, the threat detection system120 may compare the contents or routing behavior of communicationsbetween the network nodes 102-106 and a remote endpoint with the trafficmodels in the catalog. The thread detection system 120 can identify thebehavior of any of the network nodes 102-106 as being anomalous based ondetermining that a destination of the data packets sent from the networknode and/or a source of the data packets received by the network node ison the watch-list or cannot be recognized. Alternatively oradditionally, the thread detection system 120 can identify the behaviorof any of the network nodes 102-106 as being anomalous based ondetermining that the data packets collected from the network nodesufficiently match at least one of the traffic models in the catalog.

In some embodiments, the control system 130 may be a distinct computingsystem monitoring the communications between the network nodes 102-106and the remote endpoints 150. For example, the network nodes 102-106 andthe control system 120 may communicate with the network 110 via a sharedrouter or switch. The control system 130 may sniff packets on a localnetwork, e.g., a network within a local computing environment thatincludes at least the network nodes 102-106 and the control system 130.In some embodiments, the network nodes 102-106 may each be a virtualmachine and the control system 130 may be part of the virtual machinemonitor (“VMM”).

The control system 130 can collect a set of network data communicated bythe network nodes (e.g., network nodes 102-106) over the network 110.The set of network data can include at least one of: a plurality of rawdata packets over the network 110, respective source IP addresses of theplurality of raw data packets, respective destination IP addresses ofthe plurality of raw data packets, or respective data sizes of theplurality of raw data packets. The set of network data can also includeother metadata, such as the TCP/UDP port number, or the geolocation ofthe respective source or destination IP addresses. In some embodiments,the control system 130 can collect the network data, which may extendover a certain period of time or a time duration. The time duration canbe predefined as a fixed value or dynamically configured as a varyingvalue. In the case of the time duration being a varying value, thecontrol system 130 can determine the value based on, for example, anumber of network nodes actively communicating with each other acrossthe network 110, a data size of the network data collected over thenetwork 110, etc.

Upon determining the time duration, the control system 130 can segmentthe time duration into a plurality of monitoring time periods. Theamount of the monitoring time periods can be predefined as a fixed valueor dynamically configured as a varying value. In the case of themonitoring time period being a varying value, the control system 130 candetermine the value based on, for example, how long the time durationextends, a number of network nodes actively communicating with eachother across the network 110, a data size of the network data collectedover the network 110, etc. For example, the control system 130 candetermine the time duration to be a day and the monitoring period to bean hour. As such, the control system 130 can segment the time durationinto 24 monitoring time periods. In another example, the control system130 can determine the time duration to be 4 work weeks (e.g., Monday toFriday) and the monitoring period to be either work hours (e.g., 8 AM-5PM every day) or breaks (e.g., 5 PM-8 AM every day). As such, thecontrol system 130 can segment the time duration into 40 monitoring timeperiods.

Based on a plurality of timestamps included in the set of network data,the control system 130 can group the set of network data into respectivesubsets of the plurality of monitoring time periods. In someembodiments, the control system 130 can identify, from the set ofnetwork data, one or more behaviors performed by one of the networknodes 102-106 and respective timestamp(s). Based on the timestamp(s),the control system 130 can group the set of network data into respectivesubsets of the monitoring time periods. The control system 130 candetermine one or more seasonalities based on an occurrence rate, oroccurrence time(s), within each of the subset of the monitoring timeperiods. The control system 130 can then associate the behaviors withthe one or more seasonalities. Continuing with the example where the4-week time duration over which the network data extends is divided into40 monitoring periods, the control system 130 can count how many times acertain behavior has been performed (e.g., by one or more of the networknodes 102-106) during each of the 40 monitoring periods to determine theseasonality of the behavior. For instance, the control system 130 canidentify that network node 102 has regularly uploaded a fixed size offile or document during the breaks every Monday. In each of the 40monitoring time periods, the control system 130 can count how many timesthe network node 102 has performed the behavior. In response todetermining the counts, the control system 130 can determine aseasonality to be a recurring time period, e.g., the breaks everyMonday, and associate the seasonality with the behavior.

The control system 130 can communicate or interface with the threatdetection system 120 to identify, be informed, or otherwise receive oneor more behaviors performed by the network nodes 102-106 as beinganomalous. Upon identifying the behavior performed by a particularnetwork node, the control system 130 can determine with which of theendpoints and/or network nodes the behavior is intended to communicate.The control system 130 can interface with the threat detection system120 to determine whether the endpoints and/or network nodes are on theblack list, have been recognized as malicious (e.g., associated with arecognized signature), or cannot be recognized.

The control system 130 can generate a temporal profile by associating anumber of identified behaviors and respective seasonalities. Further,based on the determination by interfacing with the threat detectionsystem 120, the control system 130 can define, categorize, or otherwiseidentify the behaviors with their respective characteristics such as,for example, respective destination IP addresses (and whether the IPaddresses are associated with malicious endpoints or unrecognized),respective source IP addresses (and whether the IP addresses areassociated with malicious endpoints or unrecognized), respective datasizes (and whether the sizes are greater than a predefined threshold),etc. In some implementations, the control system 130 can generate atemporal profile that corresponds to a single host, a group of hosts, orthe entire network. In some embodiments, once the control system 130generates the temporal profile, the control system 130 can transitionitself from a data collection mode to an anomaly detection mode. In thedata collection mode, the control system 130 can allow the network nodes102-106 to continue performing the behaviors that the network nodes arecurrently performing or scheduled to perform; and in the anomalydetection mode, the control system 130 can monitor and intervene withthe behaviors that the network nodes are currently performing orscheduled to perform, or cause such behaviors to be intervened with inresponse to detecting an anomaly. In some embodiments, anomaly detectionmode can be a pure detection mode, where the control system 130 candetect anomalies based on observed behaviors without intervention.

The control system 130 can detect anomalies in a single host, group ofhosts, or the entire network based on the temporal profiles generated inthe detection mode. An anomaly has occurred when the control system 130determines that the behavior of at least one host falls outside thevalues in the predicted profile by a certain confidence margin. Forexample, the detection mode can generate temporal profiles includingseasonalities that correspond to safe network behavior (e.g., notcommunicating with malicious hosts). If the seasonalities begin todeviate from the safe behaviors included in the temporal profiles beyonda certain confidence margin, the control system 130 can identify thosebehaviors as anomalous. The control system 130 can use a highestmagnitude interaction approach to identify the network flows and/orhosts responsible for the identified anomalous behavior. In this way,the control system 130 can not only identify when anomalouscommunication patterns are occurring in a network, but also theindividual hosts and flows responsible for the anomalous behavior, whichrepresents a significant improvement over other solutions.

The control system 130 can capture and analyze network information basedon the seasonalities and temporal profiles generated in the anomalydetection mode to determine and identify other malicious hosts. Usingthe information in the temporal profiles, the control system 130 cancompare the patterns of data communication in the network 110, forexample between the nodes 102-106, with seasonalities associated withknown malicious hosts, for example the hosts blacklisted by the threaddetection system 120. The control system 130 can identify and generate atemporal profile based on the seasonalities of communications with aknown malicious host. The generated temporal profile can be used as atemporal signature to identify communications between other nodes in thenetwork that may be malicious in nature. For example, the control system130 can identify an anomalous seasonality where a node communicates 500bytes to a known malicious host every 30 minutes. This seasonality (500bytes every 30 minutes) can be compared with the hosts on the networkcommunicating with unknown endpoints. If a communication pattern issufficiently similar to the seasonality identified in this example, thecontrol system 130 can identify the unknown endpoints as being likelyinvolved in a malware infrastructure, and the unknown endpoints to theblack list of infected nodes.

The control system 130 can receive an indication from a third-party thata host on the network 110 as being compromised. The compromised hostcould be infected with malware or be communicating with a knownmalicious endpoint. The control system 130 can analyze the networktraffic associated with the identified host to identify one or moreseasonalities of the network communications. Based on the analysis, thecontrol system 130 can generate a temporal profile for the identifiednetwork host that may be used to further diagnose compromised hostselsewhere in the network. For example, the control system 130 can usethe network host to identify other potentially compromised hosts thatare communicating in the same manner as the seasonalities that werepreviously identified for the known compromised host. By tracking thesepotentially compromised hosts, the control system 130 can determine thebehavior of the potential threat as it spreads throughout the network.

The control system 130 can also capture and analyze network informationto reduce the number of false positive identifications of maliciousactivity in the network. For example, the control system 130 candetermine that a host is communicating in a seasonal way with anendpoint that is known not to be infected with malware (e.g., a softwareupdating system or a backup system). The control system 130 can generatea temporal signature for this seasonality and compare it to othercommunication patterns in the network 110 to reduce the false positiveidentifications in the network, based on the assumption that other hostscommunicating with endpoints with the same temporal profile are mostlikely using the same service, as long as the endpoints are not on theblack list of infected hosts. In this way, the control system 130 canreduce the number of false positive identifications of maliciousseasonal network behavior, which can significantly improve theperformance of the system. The control system 130 can add the endpointsdetermined to be trusted to a white list of trusted endpoints.

The control system 130 can also provide, to an analyst computing device,any of the identified anomalies along with their identified root causes.The control system 130 may transmit the information associated with theidentified anomalies via a computer network, for example network 110.The control system 130 can provide the list of malicious hosts (e.g.,the black list) to the analyst computing device, and the list of trustedhosts (e.g., the white list) to the analyst computing device. Thecontrol system 130 can provide the root cause (e.g., network flowsresponsible and/or their associated hosts) of identified anomalousnetwork behaviors to the analyst computing device. The control system130 can also provide metadata related to each of the anomalies,including host IP information, TCP/UDP port information, timestamps,network flow metadata, and any raw network data collected by the controlsystem 130. The control system 130 can also provide any seasonalityinformation collected to the analyst computing device to, including theseasonality information related to anomalous network activities. Theseasonality information can include timestamps, time intervals, datatransmission frequency, and other network seasonality information. Thecontrol system 130 can also identify and send any of the informationcommunicated as a part of an anomalous network flow, and also identifyany communication protocols used to connect any hosts in the network asa part of anomalous activities. This further allows the analystcomputing device to triage the identified anomalies and incidents, whichcan substantially reduce the false positive identification rate ofanomalous activities in the network.

In some embodiments, one or more of the systems illustrated in FIG. 1are constructed to be similar to the computing system 200 of FIG. 2. Insome embodiments, a server may be made up of multiple computing systems200. In some embodiments, a server may be a virtual server, for example,a cloud-based server accessible via the network 110. A cloud-basedserver may be hosted by a third-party cloud service host. A server maybe made up of multiple computing systems 200 sharing a location ordistributed across multiple locations. The multiple computing systems200 forming a server may communicate using the network 110. The multiplecomputing systems 200 forming a server may communicate using a privatenetwork, e.g., a network distinct from a publicly-accessible network ora virtual private network within a publicly-accessible network.

The processor 250 may be any logic circuitry that processesinstructions, e.g., instructions fetched from the memory 270 or cache275. In many embodiments, the processor 250 is a microprocessor unit,such as: those manufactured by Intel Corporation of Mountain View,Calif.; those manufactured by Motorola Corporation of Schaumburg, Ill.;those manufactured by Transmeta Corporation of Santa Clara, Calif.; theRS/6000 processor, those manufactured by International Business Machinesof White Plains, N.Y.; or those manufactured by Advanced Micro Devicesof Sunnyvale, Calif. The computing device 200 may be based on any ofthese processors, or any other processor capable of operating asdescribed herein. The processor 250 may be a single core or multi-coreprocessor. The processor 250 may be multiple processors.

The I/O interface 220 may support a wide variety of devices. Examples ofan input device 224 include a keyboard, mouse, touch or track pad,trackball, microphone, touch screen, or drawing tablet. Example of anoutput device 226 include a video display, touch screen, speaker, inkjetprinter, laser printer, dye-sublimation printer, or 3D printer. In someembodiments, an input device 224 and/or output device 226 may functionas a peripheral device connected via a peripheral interface 230.

A peripheral interface 230 supports connection of additional peripheraldevices to the computing system 200. The peripheral devices may beconnected physically, as in a FireWire or universal serial bus (USB)device, or wirelessly, as in a Bluetooth device. Examples of peripheralsinclude keyboards, pointing devices, display devices, audio devices,hubs, printers, media reading devices, storage devices, hardwareaccelerators, sound processors, graphics processors, antennae, signalreceivers, measurement devices, and data conversion devices. In someuses, peripherals include a network interface and connect with thecomputing system 200 via the network 110 and the network interface 210.For example, a printing device may be a network accessible printer.

The computing system 200 can be any workstation, desktop computer,laptop or notebook computer, server, handheld computer, mobile telephoneor other portable telecommunication device, media playing device, agaming system, mobile computing device, or any other type and/or form ofcomputing, telecommunications or media device that is capable ofcommunication and that has sufficient processor power and memorycapacity to perform the operations described herein. For example, thecomputing system 200 may comprise a gaming device such as a PlayStation(PS 1/2/3/4/x) or Personal PlayStation Portable (PSP) devicemanufactured by the Sony Corporation of Tokyo, Japan, a Nintendo, GameBoy, or Wii device manufactured by Nintendo Co., Ltd., of Kyoto, Japan,or an XBox or XBox 360 device manufactured by the Microsoft Corporationof Redmond, Wash. For example, the computing system 200 may comprise atablet device such as one of the iPad family of devices manufactured byApple Computer of Cupertino, Calif.

FIG. 3 illustrates an example model for recognizing messages. Thetraffic model 350 recognizes a communication as part of a maliciousnetwork activity. The traffic model 350 may include, for example,control information 362, an alert message 364, patterns for protocolinformation and routing information 368, content patterns 372, hashvalues 375, classification information 382, and versioning information384. In the example traffic model 350 illustrated in FIG. 3, a regularexpression 372 matches content for a Pushdo loader and a message digest375 that characterizes the binary program that generated the traffic.The Pushdo loader is malware that is used to install (or load) modulesfor use of an infected machine as a bot. For example, Pushdo has beenused to load Cutwail and create large numbers of spam bots. The trafficmodel 350 for recognizing Pushdo is provided as an example signature.

Generally, the threat detection system 120 may compare the contents orrouting behavior of communications between the network nodes 102-106 andthe remote endpoints 150 with a traffic model 350, e.g., as found in acatalog of traffic models characterizing malicious network activity. Atraffic model 350 may be generated for traffic known to be maliciousnetwork activity by identifying characteristics of the network traffic.The traffic model 350 is a type of “signature” for the identifiedmalicious network activity.

A regular expression 372 may be used to identify suspect networkcommunication. A regular expression may be expressed in any format. Onecommonly used set of terminology for regular expressions is theterminology used by the programming language Perl, generally known asPerl regular expressions, “Perl RE,” or “Perl RegEx.” (POSIX BRE is alsocommon). Network communications may be identified as matching a trafficmodel 350 if a communication satisfies the regular expression 372 in thetraffic model 350. A regular expression to match a set of strings may begenerated automatically by identifying common patterns across the set ofstrings and generating a regular expression satisfied by a commonpattern. In some embodiments, other characteristics are used as a model.For example, in some embodiments, packet length, number of packets, orrepetition of packets is used as a model. In some embodiments, contentrepetition within a packet is used as a model. In some embodiments,timing of packets is used as a model.

A message digest 375 may be used to characterize a block of data, e.g.,a binary program. One commonly used message digest algorithm is the “md5hash” algorithm created by Dr. Rivest. In some embodiments, networkcommunications may be identified if a message digest for a programgenerating or receiving the communication is equivalent to the messagedigest 375 in the traffic model 350.

Control information 362 may be used to control or configure use of thetraffic model. The example traffic model illustrated in FIG. 3 isapplied to TCP flows using port $HTTP_PORTS, e.g., 80, 443, or 8080.

An alert message 364 may be used to signal an administrator that thetraffic model has identified suspect network traffic. The alert message364 may be recorded in a log. The alert message 364 may be transmitted,e.g., via a text message or e-mail. The alert message 364 may bedisplayed on a screen. In some embodiments, a generic alert message isused. In some embodiments, an alert message is generated based onavailable context information.

Patterns for protocol information and routing information 368 mayindicate various protocols or protocol indicators for the traffic model.For example, as illustrated in FIG. 3, the Pushdo traffic uses the HTTPprotocol.

Classification information 382 may be used to indicate the type ofsuspect network activity. For example, as illustrated in FIG. 3, Pushdois a Trojan. Other classifications may include: virus, worm, drive-by,or evasive.

Versioning information 384 may be used to assign an identifier (e.g.,signature ID) and or a version number for the traffic model.

Referring now to FIG. 4, FIG. 4 illustrates a method 400 for detectinganomalous behaviors based on a temporal profile, in accordance with oneor more embodiments. Operations of the method 400 presented below areintended to be illustrative. In some embodiments, the method 400 may beaccomplished with one or more additional operations not described,and/or without one or more of the operations discussed. Additionally,the order in which the operations of the method 400 as illustrated inFIG. 4 and described below is not intended to be limiting.

In some embodiments, the method 400 may be implemented in one or moreprocessing devices (e.g., a digital processor, an analog processor, adigital circuit designed to process information, an analog circuitdesigned to process information, a state machine, and/or othermechanisms for electronically processing information). The one or moreprocessing devices may include one or more devices executing some or allof the operations of the method 400 in response to instructions storedelectronically on an electronic storage medium. The one or moreprocessing devices may include one or more devices configured throughhardware, firmware, and/or software to be specifically designed forexecution of one or more of the operations of the method 400.

In brief overview, the method 400 may include collecting a set ofnetwork data (BLOCK 402). The method 400 may include identifying one ormore seasonalities (BLOCK 404). The method 400 may include generating atemporal profile (BLOCK 406). The method 400 may include detecting ananomalous behavior (BLOCK 408). The method 400 may include extracting acharacteristic and a seasonality (BLOCK 410). The method 400 may includea determination as of whether the anomalous behavior satisfies athreshold (BLOCK 412). The method 400 may include identifying a rootcause for the anomalous behavior (BLOCK 414).

In further detail, the method 400 may include collecting a set ofnetwork data (BLOCK 402). In some embodiments, a control system (e.g.,130) can collect a set of network data communicated by network nodesover a network (e.g., the network nodes 102-106 over the network 101).The set of network data can include at least one of: a plurality of rawdata packets over the network 110, respective source IP addresses of theplurality of raw data packets, respective destination IP addresses ofthe plurality of raw data packets, or respective data sizes of theplurality of raw data packets. In some embodiments, the control system130 can collect the network data, which may extend over a certain periodof time or a time duration.

The method 400 may include identifying one or more seasonalities (BLOCK404). Based on a plurality of timestamps included in the set of networkdata, the control system 130 can group the set of network data intorespective subsets of monitoring time periods. In some embodiments, thecontrol system 130 can identify, from the set of network data, one ormore behaviors performed by one of the network nodes 102-106 andrespective timestamp(s). Based on the timestamp(s), the control system130 can group the set of network data into respective subsets of themonitoring time periods. The control system 130 can determine one ormore seasonalities based on an occurrence rate, or occurrence time(s),within each of the subset of the monitoring time periods. The controlsystem 130 can then associate the behaviors with the one or moreseasonalities.

The method 400 may include generating a temporal profile (BLOCK 406). Insome embodiments, the control system 130 can generate a temporal profilebased on the one or more identified seasonalities. The control system130 can generate the temporal profile by associating the identifiedbehaviors with the respective seasonalities. While identifying thebehaviors to be included in the temporal profile, the control system 130can interface with a threat detection system (e.g., 120) to identifyrespective characteristics of the behaviors. The characteristic caninclude respective destination IP addresses (and whether the IPaddresses are associated with malicious endpoints or unrecognized) ofthe behaviors, respective source IP addresses (and whether the IPaddresses are associated with malicious endpoints or unrecognized) ofthe behaviors, respective data sizes (and whether the sizes are greaterthan a predefined threshold) of the behaviors, etc.

The method 400 may include detecting an anomalous behavior (BLOCK 408).In some embodiments, once the control system 130 generates the temporalprofile, the control system 130 can switch to an anomaly detection mode.In such a mode, the control system 130 may detect whether any of thebehaviors in the temporal profile and/or whether any of the behaviorsthat the network nodes 102-104 is performing is anomalous based on thetemporal profile. In some embodiments, the control system 130 candetermine a behavior as being anomalous based on the detectedcharacteristic and seasonality, which shall be discussed as follows.

The method 400 may include extracting respective characteristic andseasonality of each of the behaviors (BLOCK 410). The control system 130can extract, from the temporal profile, the respective characteristicand seasonality of each of the behaviors to determine whether thebehavior shall be categorized as being anomalous. The control system 130can determine the behavior as being anomalous based on determiningwhether the characteristic and seasonality satisfy a condition (BLOCK412). The control system 130 can predefine the condition to include atleast one of: (a) whether the characteristic is associated with amalicious endpoint/network node; (b) whether the characteristic isassociated with an unrecognized endpoint/network node; (c) whether thecharacteristic is associated with a recurring time period; or (d)whether the seasonality deviates from the expected temporal profileestablished by the control system 130. If not, the method 400 mayproceed again to BLOCK 408 to detect another anomalous behavior; and ifso, the method 400 may proceed to BLOCK 414 to identify a root cause forthe anomalous behavior.

The method 400 may also include providing information related to thedetected anomalous behavior and the identified root cause of thedetected anomalous behavior to an analyst computing device. Theinformation related to the anomalous behavior can include seasonalityinformation, timestamps, network flow metadata, hosts identified thatare associated with the anomalous network behavior, and the datatransmitted as a part of the anomalous behavior. The information can betransmitted via a computer network, for example the network 110. Theanalyst computing device can triage the identified anomalies andincidents.

In an example, the control system 130 can determine, from the temporalprofile, that the characteristic of an identified behavior (e.g., adestination IP addresses) corresponds to an endpoint that was notpreviously identified and the seasonality does not conform to theexpected temporal profiles established in the detection mode. In thiscase, the control system 130 can determine the at least one of thepredefined conditions is satisfied, and thus, the control system 130 candetermine the behavior as anomalous. Further, the control system 130 candetermine the hosts and/or network flows responsible for the anomalousbehavior using highest magnitude interaction analysis. In anotherexample, the control system 130 can determine, from the temporalprofile, that the characteristic of an identified behavior (e.g., asource IP addresses) corresponds to an endpoint that was previouslyidentified as suspicious or malicious (e.g., on the black list) and theseasonality corresponds to a recurring time period (e.g., every 20hours, every week, etc.). The control system 130 can determine that atleast one of the characteristic and seasonality satisfy the predefinedconditions, and thus, the control system 130 may determine the behavioras anomalous. Further, the control system 130 can pinpoint the rootcause (e.g., the specific network flows and/or hosts responsible for theanomaly) by using highest magnitude interaction analysis on the networkbehavior. In yet another example, the control system 130 can determine,from the temporal profile, that the characteristic of an identifiedbehavior (e.g., a destination IP addresses) corresponds to an endpointthat was previously identified as suspicious or malicious (e.g., on theblack list) and the seasonality corresponds to a recurring time period(e.g., every 20 hours, every week, etc.). The control system 130 candetermine that at least one of the characteristic and seasonalitysatisfy the predefined conditions, and thus, the control system 130 maydetermine the behavior as anomalous. Further, the control system 130 canpinpoint the root cause why such a behavior is deemed as anomalous byspecifying the suspicious endpoint and recurring time period.

It should be understood that the systems and methods described above maybe provided as instructions in one or more computer programs recorded onor in one or more articles of manufacture, e.g., computer-readablemedia. The article of manufacture may be a floppy disk, a hard disk, aCD-ROM, a flash memory card, a PROM, a RAM, a ROM, or a magnetic tape.In general, the computer programs may be implemented in any programminglanguage, such as LISP, Perl, Python, C, C++, C#, PROLOG, or in any bytecode language such as JAVA. The software programs may be stored on or inone or more articles of manufacture as object code.

Having described certain embodiments of methods and systems, it will nowbecome apparent to one of skill in the art that other embodimentsincorporating the concepts of the disclosure may be used. Therefore, thedisclosure should not be limited to certain embodiments, but rathershould be limited only by the spirit and scope of the following claims.

What is claimed is:
 1. A method for monitoring a network, comprising:collecting, by a control system comprising a processor and memory, a setof network data communicated by a plurality of network nodes over anetwork during a time duration; identifying, by the control system, oneor more seasonalities from the set of network data; generating, by thecontrol system, a temporal profile based on the one or more identifiedseasonalities; detecting, by the control system and based on thetemporal profile, an anomalous behavior performed by one of theplurality of network nodes; and identifying, by the control system andbased on the temporal profile, a root cause for the anomalous behavior.2. The method of claim 1, further comprising: switching, by the controlsystem, from a data collection mode to an anomaly detection mode inresponse to the generation of the temporal profile.
 3. The method ofclaim 1, wherein the set of network data includes at least one of: aplurality of raw data packets over the network, respective source IPaddresses of the plurality of raw data packets, respective destinationIP addresses of the plurality of raw data packets, respective source TCPports of the plurality of raw data packets, respective destination TCPports of the plurality of raw data packets, respective source UDP portsof the plurality of raw data packets, respective destination UDP portsof the plurality of raw data packets, and respective data sizes of theplurality of raw data packets.
 4. The method of claim 1, furthercomprising: segmenting, by the control system, the time duration into aplurality of monitoring time periods; grouping, by the control systembased on a plurality of timestamps of the set of network data, the setof network data into respective subsets of the plurality of monitoringtime periods; and determining, by the control system, the one or moreseasonalities based on an occurrence rate associated with each of thesubset of the monitoring time periods.
 5. The method of claim 1, whereinidentifying a root cause for the anomalous behavior further comprises:determining, by the control system, a network flow associated with theanomalous behavior using highest magnitude interaction analysis; andidentifying, by the control system, the network nodes associated withthe network flow.
 6. The method of claim 1, wherein detecting ananomalous behavior performed by one of the plurality of network nodesfurther comprises: collecting, by the control system, a second set ofnetwork data communicated by the plurality of network nodes over thenetwork during a second time duration; identifying, by the controlsystem, one or more detection mode seasonalities from the second set ofnetwork data; comparing, by the control system, the detection modeseasonalities with the temporal profile to calculate a confidencemargin; and detecting, by the control system, an anomalous behaviorbased on the calculated confidence margin exceeding a predeterminedthreshold.
 7. The method of claim 1, further comprising: identifying, bythe control system, from the set of network data, a networkcommunication between two network nodes, wherein at least one of thenetwork nodes is on a list of known malicious network nodes;identifying, by the control system, one or more malicious seasonalitiesof the identified network communication; and generating, by the controlsystem, a malicious temporal profile based on the one or more identifiedmalicious seasonalities; comparing, by the control system, the one ormore seasonalities to the malicious temporal profile to determine amalicious network communication with an unknown network node; andadding, by the control system, the unknown network node to the list ofknown malicious network nodes.
 8. The method of claim 1, furthercomprising: identifying, by the control system, from the set of networkdata, a network communication between two network nodes, wherein atleast one of the network nodes is on a list of known trusted networknodes; identifying, by the control system, one or more trustedseasonalities of the identified network communication; generating, bythe control system, a trusted temporal profile based on the one or moreidentified trusted seasonalities; comparing, by the control system, theone or more seasonalities to the trusted temporal profile to determine atrusted network communication with an unknown network node; and adding,by the control system, the unknown network node to the list of knowntrusted network nodes.
 9. A computing device comprising: a memory; andone or more processors operatively coupled to the memory, the one ormore processors being to: collect a set of network data communicated bya plurality of network nodes over a network during a time duration;identify one or more seasonalities from the set of network data;generate a temporal profile based on the one or more identifiedseasonalities; detect, based on the temporal profile, an anomalousbehavior performed by one of the plurality of network nodes; andidentify, based on the temporal profile, a root cause for the anomalousbehavior.
 10. The computing device of claim 9, wherein the one or moreprocessors are further to switch from a data collection mode to ananomaly detection mode in response to the generation of the temporalprofile.
 11. The computing device of claim 9, wherein the set of networkdata includes at least one of: a plurality of raw data packets over thenetwork, respective source IP addresses of the plurality of raw datapackets, respective destination IP addresses of the plurality of rawdata packets, respective source TCP ports of the plurality of raw datapackets, respective destination TCP ports of the plurality of raw datapackets, respective source UDP ports of the plurality of raw datapackets, respective destination UDP ports of the plurality of raw datapackets, and respective data sizes of the plurality of raw data packets.12. The computing device of claim 9, wherein the one or more processorsare further to: segment the time duration into a plurality of monitoringtime periods; group, based on a plurality of timestamps of the set ofnetwork data, the set of network data into respective subsets of theplurality of monitoring time periods; and determine the one or moreseasonalities based on an occurrence rate associated with each of thesubset of the monitoring time periods.
 13. The computing device of claim9, wherein the one or more processors are further to: determine anetwork flow associated with the anomalous behavior using highestmagnitude interaction analysis; and identify the network nodesassociated with the network flow.
 14. The computing device of claim 9,wherein the one or more processors are further to: collect a second setof network data communicated by the plurality of network nodes over thenetwork during a second time duration; identify one or more detectionmode seasonalities from the second set of network data; compare thedetection mode seasonalities with the temporal profile to calculate aconfidence margin; and detect an anomalous behavior based on thecalculated confidence margin exceeding a predetermined threshold. 15.The computing device of claim 9, wherein the one or more processors arefurther to: identify, from the set of network data, a networkcommunication between two network nodes, wherein at least one of thenetwork nodes is on a list of known malicious network nodes; identifyone or more malicious seasonalities of the identified networkcommunication; and generate a malicious temporal profile based on theone or more identified malicious seasonalities; compare the one or moreseasonalities to the malicious temporal profile to determine a maliciousnetwork communication with an unknown network node; and add the unknownnetwork node to the list of known malicious network nodes.
 16. Thecomputing device of claim 9, wherein the one or more processors arefurther to: identify, from the set of network data, a networkcommunication between two network nodes, wherein at least one of thenetwork nodes is on a list of known trusted network nodes; identify oneor more trusted seasonalities of the identified network communication;generate a trusted temporal profile based on the one or more identifiedtrusted seasonalities; compare the one or more seasonalities to thetrusted temporal profile to determine a trusted network communicationwith an unknown network node; and add the unknown network node to thelist of known trusted network nodes.
 17. A non-transitory computerreadable medium storing program instructions for causing one or moreprocessors to: collect a set of network data communicated by a pluralityof network nodes over a network during a time duration; identify one ormore seasonalities from the set of network data; generate a temporalprofile based on the one or more identified seasonalities; detect, basedon the temporal profile, an anomalous behavior performed by one of theplurality of network nodes; and identify, based on the temporal profile,a root cause for the anomalous behavior.
 18. The non-transitory computerreadable medium of claim 15, wherein the program instructions furthercause the one or more processors to: collect a second set of networkdata communicated by the plurality of network nodes over the networkduring a second time duration; identify one or more detection modeseasonalities from the second set of network data; compare the detectionmode seasonalities with the temporal profile to calculate a confidencemargin; and detect an anomalous behavior based on the calculatedconfidence margin exceeding a predetermined threshold.
 19. Thenon-transitory computer readable medium of claim 15, wherein the programinstructions further cause the one or more processors to: identify, fromthe set of network data, a network communication between two networknodes, wherein at least one of the network nodes is on a list of knownmalicious network nodes; identify one or more malicious seasonalities ofthe identified network communication; generate a malicious temporalprofile based on the one or more identified malicious seasonalities;compare the one or more seasonalities to the malicious temporal profileto determine a malicious network communication with an unknown networknode; and add the unknown network node to the list of known maliciousnetwork nodes.
 20. The non-transitory computer readable medium of claim15, wherein the program instructions further cause the one or moreprocessors to: identify, from the set of network data, a networkcommunication between two network nodes, wherein at least one of thenetwork nodes is on a list of known trusted network nodes; identify oneor more trusted seasonalities of the identified network communication;generate a trusted temporal profile based on the one or more identifiedtrusted seasonalities; compare the one or more seasonalities to thetrusted temporal profile to determine a trusted network communicationwith an unknown network node; and add the unknown network node to thelist of known trusted network nodes.